I'm a bit confused: the documentation for maven-plugin-plugin says that requiredJavaVersion is evaluated by Maven 4 and ignored by earlier Maven versions..
Also, the property is marked Since: 3.8.0, but in the Flow 2.x branch the plugin version is 3.5.2

https://maven.apache.org/plugin-tools/maven-plugin-plugin/descriptor-mojo.html

So the check has been introduced also in Maven 3.9.12 (apache/maven#11479).

So the check has been introduced also in Maven 3.9.12 (apache/maven#11479).

Yes, it was just observed in one case with Vaadin 7

https://vaadin.com/forum/t/error-the-plugin-com-vaadin7-7-46-and-java-11-check/179171

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

We need to make similar PRs for all Flow, Hilla and platform maintained branches